Skip to content

Instantly share code, notes, and snippets.

Discover gists

@Nouchey
Nouchey / Wordle Hardcore Mode-2026-03-04.user.js
Last active July 8, 2026 09:04
Wordle Hardcore Mode (Tampermonkey Userscript)
// ==UserScript==
// @name Wordle Hardcore Mode
// @description Adds a more restrictive “Hard Mode” to New York Times Games' Wordle to warn the player about impossible guesses
// @version 2026-07-01
// @author Nouche
// @match https://www.nytimes.com/games/*wordle*
// @run-at document-start
// @tag games
// ==/UserScript==
@Nouchey
Nouchey / Spelling Bee State Sharing-2026-03-13.user.js
Last active July 8, 2026 09:03
Spelling Bee State Sharing (Tampermonkey Userscript)
// ==UserScript==
// @name Spelling Bee State Sharing
// @description Adds a keyboard shortcut (Ctrl-B) while playing New York Times Games' Spelling Bee to share (copy) a breakdown of the player's current game state, comparing it against the maximum values as given by that day's answers (also holding down Alt causes the output to be displayed as a browser alert instead); another shortcut (Ctrl-Q) can be used for quick sharing (#words, score rank)
// @version 2026-07-08
// @author Nouche
// @match https://www.nytimes.com/*/spelling-bee*
// @run-at document-start
// @grant none
// @noframes
// @tag games
@Naedri
Naedri / IELTS-Cheat-sheet.md
Last active July 8, 2026 09:01
IELTS Cheat sheet
@geoffreylitt
geoffreylitt / explain-diff-html.md
Last active July 8, 2026 08:57
explain-diff
name explain-diff-html
description Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

Explain Diff

Please make me a rich, interactive explanation of the specified code change.

It should have these sections:

@karpathy
karpathy / llm-wiki.md
Created April 4, 2026 16:25
llm-wiki

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

@mwchase
mwchase / Default.sublime-keymap
Last active February 23, 2021 18:52
Better reindenting for Sublime Text
// Excerpt
{ "keys": ["tab"], "command": "sane_reindent", "context":
[
{ "key": "setting.auto_indent", "operator": "equal", "operand": true },
{ "key": "selection_empty", "operator": "equal", "operand": true, "match_all": true },
{ "key": "preceding_text", "operator": "regex_match", "operand": "^$", "match_all": true },
{ "key": "following_text", "operator": "regex_match", "operand": "^$", "match_all": true }
]
}
@k16shikano
k16shikano / SKILL.md
Last active July 8, 2026 08:50
japanese-tech-writing/SKILL
name japanese-tech-writing
description 日本語の技術文書・書籍原稿の文章規範。整形（一文一行、引用ブロック、脚注、コラム記法）、段落と論証の構成（パラグラフライティング）、論証の厳密さ（ツッコミどころの除去）、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。

日本語技術文書の文章規範

日本語で技術的な原稿（書籍の章、記事、解説文）を書く・推敲するときは、以下の規範に従う。

整形